From 61296a54181484b59df7933660c8471747d9a3f4 Mon Sep 17 00:00:00 2001 From: Robert Lipe Date: Sun, 27 Oct 2019 13:41:39 -0500 Subject: [PATCH] Cleanup of dangling doc files for dead formats Formats in deprecated/ don't need live doc. Reformatted our largest xmldoc files. --- xmldoc/formats/axim_gpb.xml | 10 - xmldoc/formats/cetus.xml | 7 - xmldoc/formats/copilot.xml | 17 -- xmldoc/formats/coto.xml | 20 -- xmldoc/formats/delbin.xml | 52 ---- xmldoc/formats/garmin.xml | 174 +++++++------- xmldoc/formats/garmin301.xml | 16 +- xmldoc/formats/garmin_g1000.xml | 22 +- xmldoc/formats/garmin_gpi.xml | 10 +- xmldoc/formats/garmin_poi.xml | 3 +- xmldoc/formats/garmin_txt.xml | 14 +- xmldoc/formats/gcdb.xml | 6 - xmldoc/formats/geonet.xml | 7 +- xmldoc/formats/geoniche.xml | 7 - xmldoc/formats/google.xml | 36 --- xmldoc/formats/gpilots.xml | 10 - xmldoc/formats/gpspilot.xml | 10 - xmldoc/formats/igc.xml | 4 +- xmldoc/formats/lowranceusr.xml | 24 +- xmldoc/formats/mag_pdb.xml | 10 - xmldoc/formats/magnav.xml | 44 ---- xmldoc/formats/msroute.xml | 25 -- xmldoc/formats/msroute1.xml | 22 -- .../options/miniHomer-gps-utc-offset.xml | 1 + .../options/miniHomer-gps-week-rollover.xml | 1 + xmldoc/formats/osm.xml | 4 +- xmldoc/formats/ozi.xml | 6 +- xmldoc/formats/palmdoc.xml | 14 -- xmldoc/formats/pathaway.xml | 8 - xmldoc/formats/psp.xml | 223 ------------------ xmldoc/formats/quovadis.xml | 21 -- xmldoc/formats/unicsv.xml | 16 +- 32 files changed, 148 insertions(+), 696 deletions(-) delete mode 100644 xmldoc/formats/axim_gpb.xml delete mode 100644 xmldoc/formats/cetus.xml delete mode 100644 xmldoc/formats/copilot.xml delete mode 100644 xmldoc/formats/coto.xml delete mode 100644 xmldoc/formats/delbin.xml delete mode 100644 xmldoc/formats/gcdb.xml delete mode 100644 xmldoc/formats/geoniche.xml delete mode 100644 xmldoc/formats/google.xml delete mode 100644 xmldoc/formats/gpilots.xml delete mode 100644 xmldoc/formats/gpspilot.xml delete mode 100644 xmldoc/formats/mag_pdb.xml delete mode 100644 xmldoc/formats/magnav.xml delete mode 100644 xmldoc/formats/msroute.xml delete mode 100644 xmldoc/formats/msroute1.xml create mode 100644 xmldoc/formats/options/miniHomer-gps-utc-offset.xml create mode 100644 xmldoc/formats/options/miniHomer-gps-week-rollover.xml delete mode 100644 xmldoc/formats/palmdoc.xml delete mode 100644 xmldoc/formats/pathaway.xml delete mode 100644 xmldoc/formats/psp.xml delete mode 100644 xmldoc/formats/quovadis.xml diff --git a/xmldoc/formats/axim_gpb.xml b/xmldoc/formats/axim_gpb.xml deleted file mode 100644 index 002a0aae7..000000000 --- a/xmldoc/formats/axim_gpb.xml +++ /dev/null @@ -1,10 +0,0 @@ - - This format reads the binary (.gpb) track logs recorded on - Dell Axim Navigation Systems. - - - - This is a read-only format for now as the format was reverse - engineered and there are many unknown bytes. We can successfully - extract the common GPS data. - diff --git a/xmldoc/formats/cetus.xml b/xmldoc/formats/cetus.xml deleted file mode 100644 index ef9031f23..000000000 --- a/xmldoc/formats/cetus.xml +++ /dev/null @@ -1,7 +0,0 @@ - - - - Cetus GPS is a program for -Palm/OS. Working with Ron Parker and Kjeld Jensen, we can now read -and write files for that program. - diff --git a/xmldoc/formats/copilot.xml b/xmldoc/formats/copilot.xml deleted file mode 100644 index 6eb5272de..000000000 --- a/xmldoc/formats/copilot.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - This code is mostly intended to convert CoPilot Flight -Planner for Palm/OS" databases into other formats. You probably should -not use this to write CoPilot databases, although the code is there, -because GPSBabel doesn't convert magnetic declination values. -This version now reads all CoPilot file versions up to 4, but only -writes version 4 files. If you have a need for a version flag, please let -me know. - Questions, bug reports, etc, to ptomblin at -xcski.com - - http://xcski.com/~ptomblin/CoPilot/ -and http://navaid.com/CoPilot - - diff --git a/xmldoc/formats/coto.xml b/xmldoc/formats/coto.xml deleted file mode 100644 index 34d9a89d5..000000000 --- a/xmldoc/formats/coto.xml +++ /dev/null @@ -1,20 +0,0 @@ - -This format supports cotoGPS, a Palm GPS program. -It can read both track and marker (waypoint) files. It is currently unable -to write track files, so only marker files can be written. The marker -categories are written to and read from the icon description. The 'Not -Assigned' category leaves the icon description empty on read. -Currently geocache info is ignored. - - In addition to the documented options, this format also has a -debugging option called which takes an XCSV -delimiter value. It writes some internal values (distance, arc, x and y) -of the cotoGPS track format to the notes field. - - -Contributed by Tobias Minich. - - -cotoGPS - - diff --git a/xmldoc/formats/delbin.xml b/xmldoc/formats/delbin.xml deleted file mode 100644 index 0b36f47ed..000000000 --- a/xmldoc/formats/delbin.xml +++ /dev/null @@ -1,52 +0,0 @@ - - The 'delbin' module supports -DeLorme PN-20, -DeLorme PN-30, -DeLorme PN-40, -DeLorme PN-40 SE, and -DeLorme PN 60 receivers. - - - Not all strains of Linux are supported. Fedora 7 is known not to work, for example. - - - - - Only the 'usb:' device is supported. If you're on Windows, do not attempt to - run this through the serial driver. - - - On Linux, a name of the form 'hid:path-to-hidraw,path-to-hiddev' is also supported. - You will need to use this only if the HID device nodes on your system are not named - /dev/hidrawN and /dev/hiddevN or /dev/usb/hiddevN. - - - - This module implements the (undocumented) waypoint extensions introduced - for enhanced geocaching mode in 2.5 for PN-40 and 1.6 for PN-20. As - these are reverse engineered, there may be issues with those modes - in particular. - - - - Command to send a pocket query (GPX) to a DeLorme PN device - - - gpsbabel -i gpx -f "My Caches.gpx" -o delbin -F usb: - - - - - - If you receive a message that the device is busy, especially on Windows, - that could be because another program, likely DeLorme's own, has the - device open even though it's not actively interacting with the GPS. In - Topo 8, on the GPS tab, look for GPS Options. Uncheck "Start GPS" and - "Automatically detect GPS". Then just click the Exchange button when - you're ready for Topo to interact with the GPS. Other DeLorme software may - be similar. - - - The GPS should not be in 'map exchange' mode. When in that mode, it appears - as a disk to the USB system, thus GPSBabel will be unable to find the GPS. - diff --git a/xmldoc/formats/garmin.xml b/xmldoc/formats/garmin.xml index 4876bfcd6..9960c32d1 100644 --- a/xmldoc/formats/garmin.xml +++ b/xmldoc/formats/garmin.xml @@ -1,71 +1,71 @@ - + GPSBabel supports a wide variety of Garmin hardware via serial on most operating systems and USB on Windows, Linux, and OS X. - + For serial models, be sure the GPS is set for "Garmin mode" in setup and that nothing else (PDA hotsync programs, gpsd, getty, pppd, etc.) is using the serial port. - - Supported Garmin GPS receivers with USB include + + Supported Garmin GPS receivers with USB include -Astro -Edge 205 -Edge 305 -eTrex Legend C -eTrex Legend Cx -eTrex Legend H -eTrex Legend HCx -eTrex Summit Cx -eTrex Summit HC -eTrex Venture C -eTrex Venture Cx -eTrex Venture HC -eTrex Vista C -eTrex Vista Cx -eTrex Vista H -eTrex Vista HCx -Forerunner 205 -Forerunner 301 -Forerunner 305 +Astro +Edge 205 +Edge 305 +eTrex Legend C +eTrex Legend Cx +eTrex Legend H +eTrex Legend HCx +eTrex Summit Cx +eTrex Summit HC +eTrex Venture C +eTrex Venture Cx +eTrex Venture HC +eTrex Vista C +eTrex Vista Cx +eTrex Vista H +eTrex Vista HCx +Forerunner 205 +Forerunner 301 +Forerunner 305 Foretrex 201 -Foretrex 301 +Foretrex 301 GPS 18This model does not support transfer of waypoints, tracks, or routes, but may be used with the realtime tracking feature. -GPSMAP 195 -GPSMAP 276C -GPSMAP 295 -GPSMAP 296C -GPSMAP 378 -GPSMAP 396 -GPSMAP 478 +GPSMAP 195 +GPSMAP 276C +GPSMAP 295 +GPSMAP 296C +GPSMAP 378 +GPSMAP 396 +GPSMAP 478 GPSMAP 496 -GPSMAP 60C -GPSMAP 60CS -GPSMAP 60CSx -GPSMAP 60Cx -GPSMAP 76C -GPSMAP 76CS -GPSMAP 76CSX -GPSMAP 76Cx -GPSMAP 96 -GPSMAP 96C +GPSMAP 60C +GPSMAP 60CS +GPSMAP 60CSx +GPSMAP 60Cx +GPSMAP 76C +GPSMAP 76CS +GPSMAP 76CSX +GPSMAP 76Cx +GPSMAP 96 +GPSMAP 96C Quest Quest II Rhino 520 Rhino 530 Rhino 520 HCx Rhino 530 HCx -StreetPilot 2610 -StreetPilot 2620 -StreetPilot 2650 -StreetPilot 2720 -StreetPilot 2730 -StreetPilot 2820 -StreetPilot 7200 -StreetPilot 7500 +StreetPilot 2610 +StreetPilot 2620 +StreetPilot 2650 +StreetPilot 2720 +StreetPilot 2730 +StreetPilot 2820 +StreetPilot 7200 +StreetPilot 7500 StreetPilot c310 StreetPilot c320 StreetPilot c330 @@ -92,30 +92,30 @@ eTrex Vista eTrex (Basic Yellow) eTrex H -Forerunner 201 -Foretrex 201 -Geko 201 -Geko 301 -GPS 12CX -GPS 12Map -GPS 12 -GPS 12XL -GPS III -GPS III+ -GPS II -GPS II+ -GPS V -Rhino 110 -Rhino 120 -Rhino 130 -StreetPilot III -StreetPilot III+ +Forerunner 201 +Foretrex 201 +Geko 201 +Geko 301 +GPS 12CX +GPS 12Map +GPS 12 +GPS 12XL +GPS III +GPS III+ +GPS II +GPS II+ +GPS V +Rhino 110 +Rhino 120 +Rhino 130 +StreetPilot III +StreetPilot III+ The following Garmin GPS receivers are supported, but they do not -support Garmin communication protocol and don't work with the +support Garmin communication protocol and don't work with the option. To use these receivers, read or write GPX files from the mass storage device as mounted on your computer. @@ -234,10 +234,10 @@ GPX files from the mass storage device as mounted on your computer. - Not every feature on every model is supported. For example, + Not every feature on every model is supported. For example, while we do extract data such as heart rate and temperature from tracks on the sporting models like Edge and Forerunner, GPSBabel - is not a fitness program at its core and does not support features + is not a fitness program at its core and does not support features like workouts or calorie/fitness zone data. Furthermore, sporting models don't support track upload. When trying to upload tracks to these devices, GPSBabel converts them to courses on the fly and @@ -249,28 +249,28 @@ GPX files from the mass storage device as mounted on your computer. a speed of 10 km/h for tracks that lack them. - + To communicate with a Garmin GPS serially, use the name of that - serial port such as COM1 or /dev/cu.serial. + serial port such as COM1 or /dev/cu.serial. - To communicate via USB use usb: as the filename on all OSes. - Thus, to read the waypoints from a Garmin USB receiver and write + To communicate via USB use usb: as the filename on all OSes. + Thus, to read the waypoints from a Garmin USB receiver and write them to a GPX file: gpsbabel -i garmin -f usb: -o gpx -F blah.gpx - If you have multiple units attached via USB, you may provide - a unit number, with zero being the implied default. So if you - have three USB models on your system, they can be addressed as + If you have multiple units attached via USB, you may provide + a unit number, with zero being the implied default. So if you + have three USB models on your system, they can be addressed as usb:0, usb:1, and usb:2. To get a list of recognized devices, specify a negative number such as: gpsbabel -i garmin -f usb:-1 - - + + When reporting problems with the Garmin format, be sure to include the full unit model, firmware version, and be prepared to offer debugging dumps by adding to the command line, like: @@ -278,7 +278,7 @@ debugging dumps by adding to the command line, like: gpsbabel -D9 -i garmin -f usb: -o gpx -F blah.gpx - + Custom icons are supported on units that support that. Neither GPSBabel nor your firmware know what is associated with any given slot number. They don't know that the picture you placed in the @@ -287,28 +287,28 @@ numbered slot. GPSBabel names the them consistently with Mapsource, so they are named 'Custom 0' through 'Custom 511'. - For models where the connection on the GPS is a serial interface, + For models where the connection on the GPS is a serial interface, be sure the GPS is set for "Garmin mode" in setup and that nothing else (PDA hotsync programs, gpsd, - getty, pppd, etc.) is using the serial port. + getty, pppd, etc.) is using the serial port. For models connected via USB, we recommend use of the usb: filename. For this to work on Windows, you must install the Garmin driver. For Linux, this will fail if you have the garmin_gps - kernel module loaded. + kernel module loaded. See the Operating System Notes for details. -This module also supports realtime tracking +This module also supports realtime tracking which allows realtime position reports from a Garmin GPS receiver over USB -or serial. +or serial. -The following Garmin units do not follow the standard Garmin -communications protocol and are not supported +The following Garmin units do not follow the standard Garmin +communications protocol and are not supported by GPSBabel. Marine plotters: diff --git a/xmldoc/formats/garmin301.xml b/xmldoc/formats/garmin301.xml index f9c7d39fc..9c64d5067 100644 --- a/xmldoc/formats/garmin301.xml +++ b/xmldoc/formats/garmin301.xml @@ -1,13 +1,13 @@ - - - This is a very simple format that + + This is a very simple format that is most useful for exporting data from units that support heart rate data such as -Garmin Forerunner 301, -Garmin Forerunner 305, and -Garmin Edge 305, and + + Garmin Forerunner 301, + Garmin Forerunner 305, and + Garmin Edge 305, and to other programs for analysis. It's a simple comma delimited format that includes the timestamp, 3D position information and heart rate so you can pull it -into a spreadsheet or graphing program. - +into a spreadsheet or graphing program. + \ No newline at end of file diff --git a/xmldoc/formats/garmin_g1000.xml b/xmldoc/formats/garmin_g1000.xml index b477c2464..445521125 100644 --- a/xmldoc/formats/garmin_g1000.xml +++ b/xmldoc/formats/garmin_g1000.xml @@ -1,16 +1,16 @@ -Input format for Garmin G1000 integrated avionics system datalog generated by -G1000 system software version 563.20 or later. This datalog is automatically -generated and stored to a standard SD card if one is inserted in the *upper* -SD card slot on the G1000's MFD (right-hand display on 2-screen installations, -center display on 3-screen installations). +Input format for Garmin G1000 integrated avionics system datalog generated by +G1000 system software version 563.20 or later. This datalog is automatically +generated and stored to a standard SD card if one is inserted in the *upper* +SD card slot on the G1000's MFD (right-hand display on 2-screen installations, +center display on 3-screen installations). -Supports conversion of GPS track (including timestamp) and barometric altitude -data to any of GPSBabel's output formats. Does not include support for G1000 -stored flight plan (.fpl) route files or user waypoints. Tested on datalogs -from Cessna 182T and Turbo 182T, but it should accommodate G1000 datalogs -from other airframes as well. If any conversion failures or errors occur, -check datalog csv file for incomplete or corrupted records/rows, delete +Supports conversion of GPS track (including timestamp) and barometric altitude +data to any of GPSBabel's output formats. Does not include support for G1000 +stored flight plan (.fpl) route files or user waypoints. Tested on datalogs +from Cessna 182T and Turbo 182T, but it should accommodate G1000 datalogs +from other airframes as well. If any conversion failures or errors occur, +check datalog csv file for incomplete or corrupted records/rows, delete those records/rows from the datalog file and reattempt. diff --git a/xmldoc/formats/garmin_gpi.xml b/xmldoc/formats/garmin_gpi.xml index 0d65226bd..d46b8494e 100644 --- a/xmldoc/formats/garmin_gpi.xml +++ b/xmldoc/formats/garmin_gpi.xml @@ -12,7 +12,7 @@ but it's mangled beyond what we're likely to successfully read. - If a waypoint name is annotated with a trailing '@'NNN where NNN is + If a waypoint name is annotated with a trailing '@'NNN where NNN is a number, that number will be used as the speed for POI alerts, just as with Garmin's POI Loader program. The units default to metric kilometers per hour, but this can be changed to statute via the units argument. @@ -23,7 +23,7 @@ The layout of GPI files isn't documented and our module was created - via reverse engineering. If you get a problem on reading or writing + via reverse engineering. If you get a problem on reading or writing a GPI file, please provide that file (mailto:gpsbabel-misc@lists.sourceforge.net). @@ -36,11 +36,11 @@ This module does not support direct transfer of .GPI files to - receivers in Garmin protocol mode. For units like Nuvi, Zumo, or + receivers in Garmin protocol mode. For units like Nuvi, Zumo, or Streetpilot, just choose a file that's on the drive where your - GPS is mounted. For units like the X series (GPSMap 60CSx, GPSMap 60Cx, Legend Hcx, etc.) + GPS is mounted. For units like the X series (GPSMap 60CSx, GPSMap 60Cx, Legend Hcx, etc.) you must explicitly put the unit in mass storage mode or mount - the memory chip in an external reader and transfer the file + the memory chip in an external reader and transfer the file directly. diff --git a/xmldoc/formats/garmin_poi.xml b/xmldoc/formats/garmin_poi.xml index d807f9b90..7e0471a4d 100644 --- a/xmldoc/formats/garmin_poi.xml +++ b/xmldoc/formats/garmin_poi.xml @@ -1,5 +1,5 @@ - The Garmin POI loader + The Garmin POI loader loads custom points of interest into certain models of Garmin GPS receivers. (As of this writing, only the models introduced in 2005 and later are supported. See Garmin's site for more info.) @@ -10,4 +10,3 @@ This format was mostly useful when POI Loader couldn't read GPX and we couldn't write GPI. See GPSBabel's GPI doc. - diff --git a/xmldoc/formats/garmin_txt.xml b/xmldoc/formats/garmin_txt.xml index b9a9c88d1..62111d44d 100644 --- a/xmldoc/formats/garmin_txt.xml +++ b/xmldoc/formats/garmin_txt.xml @@ -1,23 +1,23 @@ -This is a textual format that contains nearly all of the information +This is a textual format that contains nearly all of the information contained in the MapSource main format, GDB. -This format also contains some computed values such as distances between +This format also contains some computed values such as distances between routepoints and trackpoints, speed, and course (heading). -The main goal of garmin_txt is to make aviation data more available. Because -MapSource supports only the export, GPSBabel gives you the possibility to +The main goal of garmin_txt is to make aviation data more available. Because +MapSource supports only the export, GPSBabel gives you the possibility to bring aviation data into MapSource. During the export with MapSource, some fields are written using local settings of MapSource and Windows. These include grid format, gps datum, distance and -temperature units, and the representation of date and time fields. GPSBabel -tries to read all items automatically. Problems with date and time format can +temperature units, and the representation of date and time fields. GPSBabel +tries to read all items automatically. Problems with date and time format can be solved with the 'date' and 'time' options. Command showing garmin_txt output with all options gpsbabel -i garmin_txt,date="MM/DD/YYYY",time="hh:mm:ss xx" -f in.txt -o garmin_txt,date="DD.MM.YYYY",datum="WGS 72",dist=m,prec=6,temp=c,time="HH:mm:ss",utc=+2 -F out.txt - + diff --git a/xmldoc/formats/gcdb.xml b/xmldoc/formats/gcdb.xml deleted file mode 100644 index 52a7873a7..000000000 --- a/xmldoc/formats/gcdb.xml +++ /dev/null @@ -1,6 +0,0 @@ - - This is format for the - GeocachingDB - program by DougsBrat. It works with v2 and v3 of this program. - - diff --git a/xmldoc/formats/geonet.xml b/xmldoc/formats/geonet.xml index d50bcf306..8b1378917 100644 --- a/xmldoc/formats/geonet.xml +++ b/xmldoc/formats/geonet.xml @@ -1,6 +1 @@ - - Input support for the GEOnet Names Server (GNS) country - file structure. Export to this format is not possible, as this format - has too many fields that we never get populated by any other - format. - + diff --git a/xmldoc/formats/geoniche.xml b/xmldoc/formats/geoniche.xml deleted file mode 100644 index 9b6d9c97e..000000000 --- a/xmldoc/formats/geoniche.xml +++ /dev/null @@ -1,7 +0,0 @@ - - - - Geoniche is a Palm/OS application oriented for the -off-road user. This module was contributed by Rick Richardson. - - diff --git a/xmldoc/formats/google.xml b/xmldoc/formats/google.xml deleted file mode 100644 index b8093df63..000000000 --- a/xmldoc/formats/google.xml +++ /dev/null @@ -1,36 +0,0 @@ - - - - This format is designed to read the XML emitted when you -tack "&output=js" onto the end of a Google Maps route URL (use -the "link to this page" option to get a usable URL.) This allows you -to plan a route using Google Maps, then download it and use it in your -own mapping program or GPS receiver. To get a file suitable for use -with GPSBabel, plan your route as usual with Google Maps. Once you've -got it the way you want it, click the "Link to this page" link in the -upper right-hand corner of the Google Maps page. Then, edit the URL -that appears in your address bar by adding "&output=js" (without -the quotes) onto the end. Hit enter, and the resulting page will be -mostly empty. It doesn't look like much, but it contains exactly what -GPSBabel needs. Save it to disk using whatever menu option your web -browser provides. - - -Note that if you are using Microsoft Internet Explorer, you should make sure -to save the web page as "Web Page, HTML Only". If you save it as "Web Page, -Complete", it will be reformatted into a non-XHTML format that GPSBabel -cannot read. - - -If you use a Unix-compatible -operating system, this shell script might be useful: - - -#!/bin/sh -FROM="233 S. Upper Wacker Dr, Chicago, IL" -TO="1060 W. Addison St, Chicago, IL" -wget -O - "http://maps.google.com/maps?q=$FROM to $TO&output=js" \ -2&>/dev/null >google_map.js -gpsbabel -i google -f google_map.js -o gpx -F google_map.gpx - - diff --git a/xmldoc/formats/gpilots.xml b/xmldoc/formats/gpilots.xml deleted file mode 100644 index f07a813e8..000000000 --- a/xmldoc/formats/gpilots.xml +++ /dev/null @@ -1,10 +0,0 @@ - - - - This is a Palm/OS file format for - GPilotS. - It was tested against version 6.2 of GPilotS - - Neither tracks nor routes are supported at this -time. - diff --git a/xmldoc/formats/gpspilot.xml b/xmldoc/formats/gpspilot.xml deleted file mode 100644 index 26ab9000b..000000000 --- a/xmldoc/formats/gpspilot.xml +++ /dev/null @@ -1,10 +0,0 @@ - - - - The file format for GPSPILOT gpspilot.com was provided by Ron -Parker. The output from this module has been tested with GPSPilot -Tracker v5.05sx, but it is based on reverse-engineering so it may not -work with all versions of all GPSPilot products. It had read-only -support for Airport, Navaid, City and Landmark files but will read and -write Point files. - diff --git a/xmldoc/formats/igc.xml b/xmldoc/formats/igc.xml index 4b9ff11ff..3e6445c5f 100644 --- a/xmldoc/formats/igc.xml +++ b/xmldoc/formats/igc.xml @@ -8,13 +8,13 @@ task declarations in other formats.
IGC Data Format Notes -Refer to Appendix 1 of +Refer to Appendix 1 of http://www.fai.org:81/gliding/gnss/tech_spec_gnss.asp for the specification of the IGC data format. A sample list of software applications that use data in IGC format can be -found at +found at http://www.fai.org:81/gliding/gnss/gnss_analysis_software.pdf diff --git a/xmldoc/formats/lowranceusr.xml b/xmldoc/formats/lowranceusr.xml index ef50962a7..b616c6180 100644 --- a/xmldoc/formats/lowranceusr.xml +++ b/xmldoc/formats/lowranceusr.xml @@ -1,4 +1,4 @@ - + Many Lowrance systems have the ability to output their data to an external storage device. Early models (such as iFinder Hunt) supported an MMC card. @@ -6,7 +6,7 @@ Newer models (HDS, Hook, Hook2, etc) support either an SD card or a microSD card When exported the data is saved to the card as a file. Some models have the ability to export data in GPX format but the format native to Lowrance units is called USR. -Typically the file created by the export operation will have a ".usr" suffix if is a +Typically the file created by the export operation will have a ".usr" suffix if is a native format or a ".gpx" suffix if is is a GPX format file. @@ -17,7 +17,7 @@ using different formats. Some units do not support all four elements (typically Some USR formats also have multiple element versions (i.e. USR version 4 has two different formats for storing route data). Depending on the model of device you have you may be able to select the format for export data from any of the -five USR formats or even the GPX format. +five USR formats or even the GPX format. @@ -25,20 +25,20 @@ The following provides a high-level description of the multiple USR formats that (this is based on information contained in the 2018 Lowrance Hook2 Series Operator Manual) and other sources. - User Data File version 2 - + User Data File version 2 - Legacy file format. This is the default output USR version used by GPSBabel. It contains only basic information on waypoints, routes, and trails. - User Data File version 3 - + User Data File version 3 - Legacy file format. Added depth information to Route waypoints. Supports trails with a maximum of 10,000 trail-points. Last version that supports Event Marker ICONs. - User Data File version 4 - + User Data File version 4 - Seems to be the best option for transferring data from older Lowrance units. Many of the counts (Number of Waypoints, Number of Routes, etc) were exanded from 16-bit integer values (maximum value of 65,535) to 32-bit (maxumum value 2,147,483,647) @@ -47,12 +47,12 @@ The following provides a high-level description of the multiple USR formats that - User Data File version 5 - + User Data File version 5 - Lowrance introduced universally unique identifiers (UUIDs) in this version. - User Data File version 6 - - Latest format. + User Data File version 6 - + Latest format. Supports trail characteristics speed and temperature. @@ -681,7 +681,7 @@ The following tables detail the content format of USR data files. - - - X X Route Universally Unique ID Number 16 - Appears only in USR 5 and 6 format. Universally Unique Route ID captured + Appears only in USR 5 and 6 format. Universally Unique Route ID captured as four integers @@ -1196,12 +1196,12 @@ The following tables detail the content format of USR data files. - + Some Lowrance units have the ability to export GPX (GPS Exchange Format) formatted data. Lowrance only provides minimal -support for GPX export data on their HOOK2 series (only data available to the author). Refer to +support for GPX export data on their HOOK2 series (only data available to the author). Refer to the official GPX 1.1 Schema Documentation for the complete schema. diff --git a/xmldoc/formats/mag_pdb.xml b/xmldoc/formats/mag_pdb.xml deleted file mode 100644 index eff15549d..000000000 --- a/xmldoc/formats/mag_pdb.xml +++ /dev/null @@ -1,10 +0,0 @@ - - - - With this format we support the Palm/OS export for -Map&Guide based products like "PowerRoute", -"Motorrad-Routenplaner" and (maybe) other software. The exported files -can contain maps and/or route descriptions. The reader for this format -has been tested with PowerRoute 5+6, Motorrad-Routenplaner -2002(-2006). - diff --git a/xmldoc/formats/magnav.xml b/xmldoc/formats/magnav.xml deleted file mode 100644 index 765111705..000000000 --- a/xmldoc/formats/magnav.xml +++ /dev/null @@ -1,44 +0,0 @@ - -Magellan NAV Companion for Palm/OS is not really designed -for this sort of use, but its file format is supported and with a -little bit of patience you can both read and write NAV Companion -waypoints. This conversion is based on -partially incomplete reverse-engineering of the record format, so it -may not work with all versions of NAV Companion. It has been tested -with version 2.10 and 3.20. - - -Translating NAV Companion waypoints to another format is as easy -as with any other format. Just find the Companion_Waypoints database -in your palm backup directory and use it as the input file. - - -When translating waypoints back to NAV Companion, though, you need -to jump through some hoops: - - -First, you must merge any waypoints that already exist in the database -in your Palm Backup directory with the ones you are adding; failure to -do so will result in only the new points being available in NAV Companion, -even if you give the new database a different name (it will overwrite -the old database, even in your backup directory. That's a feature of -PalmOS, not of NAV Companion.) - - -To merge the databases, use a command line like the following: - -gpsbabel -i magnav -f Companion_Waypoints.PDB -i geo -f geocaching.loc -o magnav -F merged.pdb - -Second, you must use the installer to install your new PDB file. Don't -make the mistake of copying it over the existing Companion_Waypoints.PDB -file; the one on the handheld will overwrite it rather than merging with -it. - - -Finally, because NAV Companion is not designed to work with desktop -applications, you must tell NAV Companion that its waypoints database -has changed out from under it. One way to do this is to go to the -waypoints screen and attempt to scroll; that will force it to reread -the database and fix the record pointers that it keeps on the heap. - - diff --git a/xmldoc/formats/msroute.xml b/xmldoc/formats/msroute.xml deleted file mode 100644 index 1ce5744c7..000000000 --- a/xmldoc/formats/msroute.xml +++ /dev/null @@ -1,25 +0,0 @@ - - Input support for Microsoft AutoRoute 2002-2006 .axe files - and Microsoft Streets and Trips .est files. This is for reading routes - created this program and is different than the - s_and_t format used for writing pushpins. - These files contains only routes. We can extract the coordinates and - the names of the points within route. An export to this format will - not be supported. - - - - Only the start, stops, and end points are stored in the - .est/.axe/.ptm files. Turn-by-turn route data is not stored in the - .est/.axe/.ptm files, and is recalculated by the Microsoft title each - time on opening the file. This means that the output of GPSBabel will - not contain turns needed for driving directions. - - - One possible approach to achieve similar results is to - use the Streets and Trips drawing tools to trace a line over the - interesting parts of the route to capture intersections or key turns. - GPSBabel will capture stops in the route and insert those as turns, so - adding stops at intersections can also improve the results when converting. - - diff --git a/xmldoc/formats/msroute1.xml b/xmldoc/formats/msroute1.xml deleted file mode 100644 index d1d4d36b2..000000000 --- a/xmldoc/formats/msroute1.xml +++ /dev/null @@ -1,22 +0,0 @@ - - - - Input support for Microsoft AutoRoute 2002-2006 .axe files -and Microsoft Streets and Trips .est files. This is for reading routes -created this program and is different than the -s_and_t format used for writing pushpins. -These files contains only routes. We can extract the coordinates and -the names of the points within route. An export to this format will -not be supported. - Only the start, stops, and end points are stored in the -.est/.axe/.ptm files. Turn-by-turn route data is not stored in the -.est/.axe/.ptm files, and is recalculated by the Microsoft title each -time on opening the file. This means that the output of GPSBabel will -not contain turns needed for driving directions. - One possible approach to achieve similar results is to -use the Streets and Trips drawing tools to trace a line over the -interesting parts of the route to capture intersections or key turns. -GPSBabel will capture stops in the route and insert those as turns, so -adding stops at intersections can also improve the results when converting. - - diff --git a/xmldoc/formats/options/miniHomer-gps-utc-offset.xml b/xmldoc/formats/options/miniHomer-gps-utc-offset.xml new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/xmldoc/formats/options/miniHomer-gps-utc-offset.xml @@ -0,0 +1 @@ + diff --git a/xmldoc/formats/options/miniHomer-gps-week-rollover.xml b/xmldoc/formats/options/miniHomer-gps-week-rollover.xml new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/xmldoc/formats/options/miniHomer-gps-week-rollover.xml @@ -0,0 +1 @@ + diff --git a/xmldoc/formats/osm.xml b/xmldoc/formats/osm.xml index 9ebc8ed62..0dc4d3bf3 100644 --- a/xmldoc/formats/osm.xml +++ b/xmldoc/formats/osm.xml @@ -1,5 +1,5 @@ - This format is used to exchange data with the OpenStreetMap project. + This format is used to exchange data with the OpenStreetMap project. The main goal of this collaborative project is to create free editable maps. @@ -8,6 +8,6 @@ negative numbers will be used as identifier. This has been tested with JOSM. - Because the resulting timestamps of OSM ways differ from real GPS tracks, + Because the resulting timestamps of OSM ways differ from real GPS tracks, we read OSM ways into routes. On the output side we write all available routes and tracks into the osm target file. diff --git a/xmldoc/formats/ozi.xml b/xmldoc/formats/ozi.xml index 00d9bafd4..13a3e441a 100644 --- a/xmldoc/formats/ozi.xml +++ b/xmldoc/formats/ozi.xml @@ -1,5 +1,3 @@ - - OziExplorer Waypoint Format - Another CSV format file. +OziExplorer Waypoint Format - Another CSV format file. Tested against OziExplorer v 3.90.3a / Shareware. Contributed by Alex Mottram - - + \ No newline at end of file diff --git a/xmldoc/formats/palmdoc.xml b/xmldoc/formats/palmdoc.xml deleted file mode 100644 index febf0a466..000000000 --- a/xmldoc/formats/palmdoc.xml +++ /dev/null @@ -1,14 +0,0 @@ - - PalmDoc output is similar to Text - output, except that it generates a Palm Database (PDB) file suitable for - use with programs like CSpotRun, TealDoc, AportisDoc, Palm Reader, and - others. The resulting file also contains bookmarks to make it easy to jump - to a particular waypoint. - - - The following command line reads a GPX file with Groundspeak extensions - and writes a Palm document with encrypted hints and logs: - -gpsbabel -i gpx -f 12345.gpx -o "palmdoc,dbname=Unfound Geocaches,encrypt,logs" -F 12345.pdb - - diff --git a/xmldoc/formats/pathaway.xml b/xmldoc/formats/pathaway.xml deleted file mode 100644 index 8310068c0..000000000 --- a/xmldoc/formats/pathaway.xml +++ /dev/null @@ -1,8 +0,0 @@ - - PathAway is a Palm software designed for handling "most" - GPS devices (including BlueTooth). In this time (I mean 2005) a free - tool to convert this database is located on the homepage of PathAway - (www.pathaway.com). But I've read there ... for windows and the output - formats are also very limited. - - diff --git a/xmldoc/formats/psp.xml b/xmldoc/formats/psp.xml deleted file mode 100644 index eeaf6d185..000000000 --- a/xmldoc/formats/psp.xml +++ /dev/null @@ -1,223 +0,0 @@ - -Microsoft's PocketStreets 2002 Pushpin (.PSP) format is -not yet completely documented. The .PSP module does not work with -MS Streets & Trips 2002 .EST files To create .PSP files from -Streets & Trips 2002, you will need to have PocketStreets support -installed. - - -Please note that MS Streets & Trips only exports -.PSP files. It does not import them. MS Streets & Trips 2002 only -imports CSV files. To use .PSP files, simply copy them over to the -same folder on the mobile device as the map (.MPS), and open -PocketStreets. It should also be noted that in the case a pushpin is -outside of the exported map area, the pin will be "grayed-out" and -unused in PocketStreets. This is a good thing as it allows us to -create one big .PSP file that covers multiple .MPS files. -Unfortunately, you need one .PSP file for every .MPS file. - -
-Frequently Asked Questions - - - - -Why should I use GPSBabel/psp to make pushpins when Streets & Trips (S&T) - already does that for me? - - - - -GPSBabel/psp has the advantage of being able to create pushpins -without - creating the associated map file and the need to "import" the waypoint - data into S&T. Through a series of scripts, you can create a dozen - or so PSP files in a few seconds as opposed to a few weeks using the - S&T interface. The maps are not going to change between sessions, - only the pins will. Why waste all that time creating maps when all you - really want are updated pins? As an aside, GPSBabel/psp creates points - with the proper coordinates - where S&T does not in some areas of the U.S. - (Nashville, TN for instance). - - - - - - -I keep getting a blank (32 byte) PSP file. - - - - -There are either no points to write, or you have botched the command - line for GPSBabel. GPSBabel is sensitive to UPPER and lower case - on the command line. A simple command line to create PSP files - looks like this: - -gpsbabel -i geo -f geocaching.loc -o psp -F NewOrleans.psp - - Note the use of "-f" for INPUT files and "-F" for OUTPUT files. - - - - - - -I've created a PSP file, now what do I do with it? - - - - -To use pushpins in Pocketstreets, you need to have both a map and a - pushpin file. These two files must exist in the same folder and have - exactly the same base name as the map. For example, the pins that - correspond to the map "NewOrleans.mps" should be named "NewOrleans.psp". - - - - - - -I don't have a map. What do I do now? - - - - -Create one using the "Export map to Pocketstreets" option in S&T. You - can also pick up some major city maps on the web from the MS Pocketstreets - website if you are interested in seeing how it works. - - - - - - -I have .EST files, not .PSP files. What's up with that? - - - - -In order to make PSP files, you need to use the "Export map to - Pocketstreets" function in S&T. .EST files are for use in S&T, not - Pocketstreets. - - - - - - - The .PSP files differ when I use GPSBabel/psp versus Pocketstreets to - create them. What's up? - - - - -Pocketstreets makes corrections to the S&T waypoint data upon initial - loading. GPSBabel/psp writes PSP files with these corrections already made. - Ask MS. - - - - - - -Does GPSBabel/psp work with (Autoroute, Mappoint, etc..) .PSP files? - - - - -As of this writing, I haven't seen any so I can't be sure. If they - follow the same layout as S&T 2002, I'd imagine so. - - - - - - - Does GPSBabel/psp work with (S&T 2001, S&T 2002, etc...) files? - - - - -MS changed the file layout between S&T 2001 and S&T 2002. The GPSBabel psp - module is known to work fine with S&T 2002 and 2003. - - - - - - -Does GPSBabel/psp work with (insert your country/location here) maps? - - - - -If it doesn't, feel free to inquire on the -GPSBabel-Misc -mailing list. - - - - - - -What do you mean S&T writes points with the wrong coordinates? - - - - -At some point in the "Export map to Pocketstreets" function in S&T, - it goofs the lat/long data. Points in Nashville tended to shift - 1.4 miles WEST of their original location. I'm not a geometry buff, - but I'd imagine they have a reference point for generating coordinates - that's wrong in (at least) that area. - - - - - - -I have 800 waypoints that cover a dozen or so Pocketstreets maps. - Do I need to to split my points up into smaller chunks to match the - area covered by the maps? - - - - - No. Pocketstreets will "ignore" points that are outside of the map - area. Points that are not on the current map will be "grayed out" - in pushpin explorer in Pocketsreets. This is the reason the PSP - module was written for GPSBabel in the first place. - - - - - - -Where can I find documentation for the layout of PSP files? - - - - -Just about everything I know about the PSP file format is documented - in the source. To the best of my knowledge, there is no documentation - (and for good reason, I've come to discover). - - - - - - -I have some other problem, what do I do? - - - - -Ask your question on the GPSBabel-Misc mailing list. - - - - -
- diff --git a/xmldoc/formats/quovadis.xml b/xmldoc/formats/quovadis.xml deleted file mode 100644 index 516601e76..000000000 --- a/xmldoc/formats/quovadis.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - QuoVadis for Palm OS marcosoft.com is a program for -Palm/OS. Working with record definitions provided by MarcoSoft and -further experimentation by Bruce Thompson and "Fuzzy" from the -Geocaching Forums to nail down the format precisely. - Should work fine for import and export. - One thing of note, QuoVadis stores all waypoints in a -single Palm Database without using categories. This means that it may -be difficult to keep personal waypoints separate from generated -waypoints. What Bruce recommends is taking the QuoVadisMarkerDB.PDB -file synced down from your Palm Powered device and extract the -waypoints you personally set to a GPX file. Then using GPSBabel's -joining capabilities generate a new PDB file from the personal file -and the other waypoint files of interest. - Currently the selection of icons to display and the scale -at which to display them is hardcoded. Also there is no support for -notes associated with waypoints. This will be addressed in a future -revision. - diff --git a/xmldoc/formats/unicsv.xml b/xmldoc/formats/unicsv.xml index 15f7f1889..ba2884778 100644 --- a/xmldoc/formats/unicsv.xml +++ b/xmldoc/formats/unicsv.xml @@ -1,6 +1,6 @@ Unicsv examines the first line of a file to determine the field - order and field separator in that file. On write, it tries to + order and field separator in that file. On write, it tries to figure out what data it has and writes headers and all the data it can. @@ -29,7 +29,7 @@ diff = Geocache difficulty ele = Elevation (in meters) of the point. Add "ft" or "feet" for feet. e/w = 'e' for eastern hemisphere, 'w' for western - exported = Geocache export date + exported = Geocache export date found = Geocache last found date fix = 3d, 2d, etc. gcid = Geocache cache id @@ -74,11 +74,11 @@ y_pos = Latitude z = Altitude (elevation). See "elevation". - We support some enhanced Garmin attributes. They are also available in - gpx, gdb, - garmin_gpi and partly - garmin_txt. These entities are currently - not visible in MapSource (6.12.4), but are NOT dropped + We support some enhanced Garmin attributes. They are also available in + gpx, gdb, + garmin_gpi and partly + garmin_txt. These entities are currently + not visible in MapSource (6.12.4), but are NOT dropped when working with GDB (version 3) or GPX files. Please note, that these do NOT provide a geocoding service; don't expect @@ -98,7 +98,7 @@ A typical file may be: - Name, Latitude, Longitude, Description + Name, Latitude, Longitude, Description GCEBB,35.972033,-87.134700,Mountain Bike Heaven by susy1313 GC1A37,36.090683,-86.679550,The Troll by a182pilot & Family -- 2.30.2